|
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects. == Introduction == The class diagram is the main building block of object oriented modelling. It is used both for general conceptual modelling of the systematics of the application, and for detailed modelling translating the models into programming code. Class diagrams can also be used for data modeling. The classes in a class diagram represent both the main objects, interactions in the application and the classes to be programmed. In the diagram, classes are represented with boxes which contain three parts: * The top part contains the name of the class. It is printed in bold and centered, and the first letter is capitalized. * The middle part contains the attributes of the class. They are left-aligned and the first letter is lowercase. * The bottom part contains the methods the class can execute. They are also left-aligned and the first letter is lowercase. In the design of a system, a number of classes are identified and grouped together in a class diagram which helps to determine the static relations between those objects. With detailed modelling, the classes of the conceptual design are often split into a number of subclasses. In order to further describe the behaviour of systems, these class diagrams can be complemented by a state diagram or UML state machine.〔Scott W. Ambler (2009) (UML 2 Class Diagrams ). Webdoc 2003-2009. Accessed Dec 2, 2009〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「class diagram」の詳細全文を読む スポンサード リンク
|